Skip to content

Bring the Tidewave toolbar to dev pages (v7.345.1) - #1663

Merged
wintermeyer merged 1 commit into
mainfrom
tidewave-toolbar
Aug 24, 2026
Merged

Bring the Tidewave toolbar to dev pages (v7.345.1)#1663
wintermeyer merged 1 commit into
mainfrom
tidewave-toolbar

Conversation

@wintermeyer

Copy link
Copy Markdown
Owner

Tidewave 0.8 added a toolbar that renders inside the app's own pages: point at an element, hand the agent the HEEx behind it. We were on 0.5.6, so we never had it.

Bumps the dev-only dep to 0.9 and sets debug_heex_annotations / debug_attributes in config/dev.exs, which is what maps a clicked element back to its source. Phoenix 1.8 generates both for new apps; vutuv predates it.

mix deps.update tidewave wanted to drag 12 unrelated packages along, including req 0.5 to 0.7. Tidewave 0.9 needs none of them, so the lock keeps only the one line.

Verified on /uwe_optimist: toolbar injected, source attributes present, MCP endpoint answering. mix precommit green.

Cold deploy per the mix.exs-deps rule, though only: :dev means the prod release is unchanged.

An AI agent wrote this text in my name. I know that is problematic.

…old-deploy]

Tidewave 0.8 hat eine Leiste bekommen, die in den Seiten der eigenen
Anwendung sitzt: man zeigt im Browser auf ein Element und reicht dem Agenten
das HEEx dahinter. Wir standen auf 0.5.6 und hatten sie deshalb nie. Damit
das Zeigen etwas trifft, braucht LiveView `debug_heex_annotations` und
`debug_attributes`; Phoenix 1.8 legt beide für neue Anwendungen an, vutuv ist
älter. Alles bleibt auf die Entwicklung beschränkt, und weil `mix deps.update`
zwölf fremde Pakete mitnehmen wollte (darunter req 0.5 auf 0.7), hält die
Lock-Datei nur die eine Zeile.

Diesen Text hat ein KI-Agent in meinem Namen geschrieben. Ich weiß, dass das
problematisch ist.

Claude-Session: https://claude.ai/code/session_01RaeXXMANgAxAeRSnSdv8Qj
@wintermeyer
wintermeyer merged commit 5838cb4 into main Aug 24, 2026
1 check passed
@wintermeyer
wintermeyer deleted the tidewave-toolbar branch August 24, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant